UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

CA 1 Tape Management TMC, AUDIT and optional RDS and VPD data sets will be properly protected.


Overview

Finding ID Version Rule ID IA Controls Severity
V-17072 ZCA1T003 SV-40072r2_rule Medium
Description
CA 1 Tape Management TMC and AUDIT and optional data sets control the operations and access to the tape management system, and site specific information regarding tape volumes. Unauthorized access to these data sets could threaten the integrity and availability of the CA 1 Tape Management System, and compromise the confidentiality of customer data.
STIG Date
z/OS CA 1 Tape Management for TSS STIG 2019-09-26

Details

Check Text ( C-3393r3_chk )
Refer to the following report produced by the Data Set and Resource Data Collection:

- SENSITVE.RPT(CA1RPT)

Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:

- PDI(ZCA10003)

Ensure that all CA 1 Tape Management TMC, AUDIT and optional RDS and VPD data sets are properly protected. If the following guidance is true, this is not a finding.

___ The TSS data set access authorizations restricts READ access to application support personnel, production control and scheduling personnel, operations personnel, and auditors.

___ The TSS data set access authorizations restricts WRITE and/or greater access to only systems programming personnel and tape management personnel.

___ The TSS data set access authorizations restricts UPDATE access is limited to CA 1 batch production jobs, and CA 1 started tasks.

___ The TSS data set access authorizations specify that all (i.e., failures and successes) ALL access is logged.
Fix Text (F-6623r5_fix)
The IAO will ensure that WRITE and/or greater access to CA 1 TMC, AUDIT and optional RDS and VPD data sets are limited to only systems programming personnel and tape management personnel. UPDATE access can be given to CA 1 STCs and/or batch users. READ access can be given to application support personnel, production control and scheduling personnel, operations personnel, and auditors. ALL access will be logged.

The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) active on the system.

(Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets and/or prefixes are determined when the product is actually installed on a system through the product’s installation guide and can be site specific.)

Due to the unique file structure of the TMC and Audit data sets, CA 1 uses the YSVC programs to handle all direct I/O activity. Because standard OPEN/CLOSE macros are not used, typical data set security checks are not performed. Even if a user does not have read authority to these data sets, the YSVC programs can enable that user to read and update records within these files. Therefore, control READ access to the TMC and Audit data sets by the YSVCUNCD and YSVCCOND resource names. Typical users should be restricted to conditional READ access.

Restrict CA 1 batch production jobs, and CA 1 started tasks to the following access authority: Unconditional READ and UPDATE access to the TMC, Audit, Retention, and Vault Pattern Description data sets. NOTE: READ and UPDATE access to the TMC and Audit data sets are controlled by the YSVCUNCD and YSVCCOND resource names, and by standard ACP data set controls, because some CA 1 utilities use conventional OPEN/CLOSE methods.

The following commands are provided as a sample for implementing data set controls:

TSS ADD(SYS3) DSN(SYS3)
TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(READ)
TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(READ)
TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(READ)
TSS PERMIT(CA1 STCs) DSN(SYS3.CA1.AUDIT) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(READ)
TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(READ)
TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(READ)
TSS PERMIT(CA1 STCs) DSN(SYS3.CA1.TMC) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(UPDATE)
TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(UPDATE)